What is it?

• Bug

Description

With qwikDevtools() or qwikMcp() enabled, Alt+click (click-to-source) opens the editor several lines below the element you clicked. On the MCP SSR fixture the counter button is on line 5 of routes/index.tsx, and data-qwik-inspector says routes/index.tsx:14:5, past the end of a 10 line file. Without either plugin it says 5:5.

Both plugins instrument component files (and DevTools also root.tsx) in a pre transform, before the Qwik optimizer: an import at the top, const collecthook = ... at the start of each component, a multi-line collecthook({...}) after every hook, and <QwikDevtools /> before </body>. Every one of those added lines. The optimizer computes dev locations from the text it receives and takes no input sourcemap, so returning a sourcemap from the transform wouldn't help here.

The fix keeps the instrumentation but never adds a line: the imports go on line 1, the init goes right after the component's {, each collecthook(...) is appended on its hook's line (with a ; when the statement relies on ASI), and <QwikDevtools /> sits right before </body>. The rule is written next to both transform hooks so it doesn't regress.

What it doesn't fix:

• columns can still be off on a line that got an insertion, e.g. JSX on the same line as the component's opening {
• QRLDev lo/hi are byte offsets, so they still move. Getting those right would mean instrumenting after the optimizer, which is a bigger change

There's also a separate one-line commit fixing the type of the birpc resolver from #9123, which made @qwik.dev/mcp fail its typecheck.

Tests: a unit test checks that both transforms keep every source line on its line number and still parse, and the MCP integration test now asserts data-qwik-inspector ends with routes/index.tsx:5:5. That assertion fails on main with 14:5.

Demo

Alt+click on the same button, before and after. The banner shows the location the editor was asked to open and what is actually on that line.

Checklist

• My code follows the developer guidelines of this project
• I performed a self-review of my own code
• I added a changeset with pnpm change
• I added new tests to cover the fix / functionality